-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: 0.31.1 #585
Merged
stainless-app
merged 8 commits into
main
from
release-please--branches--main--changes--next
Jul 15, 2024
Merged
release: 0.31.1 #585
stainless-app
merged 8 commits into
main
from
release-please--branches--main--changes--next
Jul 15, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 11, 2024 05:01
850c8e9
to
0a0edce
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 11, 2024 10:22
dcda82a
to
f7e49f2
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
3 times, most recently
from
July 13, 2024 05:01
b84614b
to
1d9db4f
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
2 times, most recently
from
July 15, 2024 05:01
645f126
to
fabd591
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 15, 2024 07:17
9322d26
to
a71927b
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
2 times, most recently
from
July 15, 2024 10:16
6460112
to
f52b5fe
Compare
tests/lib/test_bedrock.py
Outdated
|
||
@pytest.mark.respx() | ||
def test_messages_retries(respx_mock: MockRouter) -> None: | ||
respx_mock.post(re.compile(r"https://bedrock-runtime.us-east-1.amazonaws.com/model/.*/invoke")).mock( |
Check failure
Code scanning / CodeQL
Incomplete regular expression for hostnames High test
This regular expression has an unescaped '.' before 'amazonaws.com/model/', so it might match more hosts than expected.
tests/lib/test_bedrock.py
Outdated
@pytest.mark.respx() | ||
@pytest.mark.asyncio() | ||
async def test_messages_retries_async(respx_mock: MockRouter) -> None: | ||
respx_mock.post(re.compile(r"https://bedrock-runtime.us-east-1.amazonaws.com/model/.*/invoke")).mock( |
Check failure
Code scanning / CodeQL
Incomplete regular expression for hostnames High test
This regular expression has an unescaped '.' before 'amazonaws.com/model/', so it might match more hosts than expected.
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 15, 2024 11:29
05900c0
to
f68c81d
Compare
samj-anthropic
approved these changes
Jul 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.31.1 (2024-07-15)
Full Changelog: v0.31.0...v0.31.1
Bug Fixes
Chores
next
(#587) (f7e49f2)This Pull Request has been generated automatically as part of Stainless's release process.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request (see details).
More technical details can be found at stainless-api/release-please.